fix(components): exclude test files from the published stylesheet's @source scan - #8453

Fixes #8446

Tailwind v4 scans source text, not an import graph. packages/components/src/index.css
declared @source '../src/**/*.{ts,tsx}' with no exclusion, so all 243 test files under
src/**/__tests__/ were sources for the published dist/index.css. A class-shaped token
written as a test's expected value therefore compiled a real utility into the shipped
bundle — which is how a test can create the production utility it is asserting on.

The single cleanest instance found here is not a fixture but an assertion:

packages/components/src/renderers/basic/__tests__/icon-unresolvable-placeholder.test.tsx:146
    expect(svg?.getAttribute('class')).toContain('text-green-500');

.text-green-500 shipped in dist/index.css because that assertion names it.

Two @source not lines are added, matching the spelling already used by fields,
plugin-grid and plugin-kanban.

The measurement

src/index.css compiled through this package's own pipeline — postcss([tailwindPostcss()]),
i.e. step 2 of packages/components/scripts/build-css.mjs — and every Rule node collected
with its at-rule ancestry. Diffing rule sets, not counting them.

File set on disk for both readings (this is the step whose omission would make the table
dishonest — the compile is sensitive to what is on disk, not to what is committed):

• Working tree exactly 0b1ac58a66ee8ee0ddc59e0fa73301f8647ffbf6; git status --porcelain
  over packages/components/src empty for the before reading.
• 453 .ts/.tsx files under packages/components/src, 243 of them test-shaped.
• After reading: the same tree plus this PR's two @source not lines. The new guard test
  file was added afterwards and verified not to change the sheet (byte-identical rule set),
  so it does not contaminate the table.

⚠️ And the working directory, which turned out to matter more than the file set.
src/index.css opens with a bare @import 'tailwindcss', so Tailwind's automatic source
detection is ON and — as packages/fields/src/index.css already documents — resolves against
the process CWD. Same commit, same bytes, two artifacts:

A repo-root reading would have under-reported this PR's removal by five of eight classes —
they survive there only because other packages' sources also name them. The table below is
the package-CWD one.

What disappears — the rule diff

Removed (8). Added (0).

@layer utilities || .flex-grow
@layer utilities || .flex-nowrap
@layer utilities || .h-\[125px\]
@layer utilities || .isolate
@layer utilities || .paused
@layer utilities || .shrink
@layer utilities || .text-green-500
@layer utilities || .w-\[250px\]

Per-class verdict: does any non-test source name it?

The compile diff defines the answer — a rule that disappears when test files stop being
scanned is by construction sourced only from test files. The greps below say which text
produced it. All eight: no production namer.

Four of the eight were compiled out of English prose in comments. None was ever authored
as styling.

Does removing them bite anyone?

• Apps that run their own Tailwind — every example app here does (apps/console,
  examples/console-starter, examples/byo-backend-console all @source the package src
  dirs) — generate utilities from their own markup and are unaffected.
• Authored runtime metadata was already unsupported. The 2026-06-30 amendment to ADR-0080
  under ADR-0065 (content/docs/guide/react-pages.md) states a utility class in page source
  "produces CSS only if that exact class happens to already appear in objectui's own source",
  and os validate warns page-source-className-tailwind. That incidental "happens to
  appear" is precisely what is being removed.
• The narrow case that can regress: an app importing only the prebuilt
  @object-ui/components/style.css, running no Tailwind of its own, hand-writing one of the
  eight in its own JSX. .isolate, .shrink, .flex-nowrap, .text-green-500 are plausible
  there. .flex-grow and .shrink also have surviving canonical spellings — .grow and
  .shrink-0 stay in the sheet, and this repo already migrated flex-grow-N → grow-N
  deliberately.

That residual case is why the changeset is minor rather than patch.

Proving the change can fail

The instrument is the compiled stylesheet, so the ablation restores the unrestricted
@source and recompiles. Run from the committed implementation (336bd7a4), tree clean,
with a trap ... EXIT INT TERM holding absolute paths.

Mutation proven on disk, not by an exit code: @source not lines 2 → 0; git hash-object
50c2d90f vs git rev-parse HEAD:packages/components/src/index.css = 75153ac5.

Both legs fire:

1. The rules come back — all eight reappear in the recompiled sheet. So does a ninth,
   .mt-\[3\.7331px\]: the guard test's own sentinel. That is the defect reproducing live on
   this PR's own new test file, and it is what proves the probe is not inert.
2. The guard test goes red — vitest exits 1 on
   AssertionError: expected '/*! tailwindcss v4.3.3 …' not to contain '3.7331px'.

Restore proven by state: git diff HEAD empty, git hash-object back to 75153ac5,
@source not lines back to 2 — then the guard test passes again.

No dist/ rebuild is involved: the reading compiles src/index.css fresh each time, so there
is no stale-artifact leg to get wrong here.

The guard test

src/__tests__/index-css-scan-excludes-tests.test.ts compiles the stylesheet and asserts
both directions, because a stylesheet compiled from nothing satisfies "no test-sourced
rules" — an implementation strictly worse than this fix (delete the @source line) would pass
a negative-only test.

• Negative: a sentinel arbitrary-value token (mt-[3.7331px], absent everywhere else in
  the repo) is written in that test file itself, which lives under __tests__/. The probe
  is self-hosted: remove the exclusions and the sentinel compiles and the test goes red. It
  does not depend on any other test continuing to name a fixture class.
• Positive: .flex-col (production-sourced) must be present, and the sheet must hold more
  than 800 rules.

It passes base: packageRoot to @tailwindcss/postcss so the reading is CWD-independent —
otherwise Vitest (repo root) and pnpm build (package dir) would measure different artifacts,
per the table above.

Out of scope — reported, not swept in (#8446 fences this to components)

search_issues was rate-limited, so per the dispatch these are reported rather than filed
unsearched. None is fixed here.

1. The issue says components is the only one of three missing this. There are more.
   Sweep of every @source in the repo: excluding correctly — fields (filename only),
   plugin-grid (not mentioned in the issue), plugin-kanban. Missing exclusions
   entirely — packages/runner/src/index.css, apps/console/src/index.css,
   apps/site/app/global.css, and both examples/*/src/index.css.
2. packages/runner is a published package that re-leaks these exact classes. Its
   index.css scans ../../packages/components/src/** with no test exclusion, so after
   this PR @object-ui/runner's own published sheet still compiles the eight. Its line 10 also
   reads @source './src/**/*.{ts,tsx}', which from packages/runner/src/index.css resolves
   to packages/runner/src/src/ — a directory that does not exist.
3. components lacks source(none), so its published sheet is CWD-dependent (1385 vs 3430
   rules, table above) and non-shipped text is a source. Measured: adding
   source(none) on top of this PR removes 23 further rules, including .flex-shrink-0,
   .bg-blue-500, .md:text-2xl, .hover:bg-blue-700:hover and — from a doc comment —
   .origin-[--radix-…] with a literal Unicode ellipsis. fields calls its own source(none)
   "load-bearing, not tidiness" for exactly this reason. This PR's two lines are a strict
   improvement but only a partial fix of the false-green generator; the complete fix is
   sibling parity on source(none), which is a materially larger bundle diff and its own card.
4. packages/components/CHANGELOG.md is a Tailwind source for the published bundle.
   Proven by injecting a unique token into it and recompiling. .flex-shrink-0 — a deprecated
   v3 alias this repo deliberately migrated away from — ships today solely because the
   changelog entry announcing its removal names it.

Changeset

.changeset/8446-components-css-excludes-test-sources.md — @object-ui/components: minor.

node scripts/check-changeset-presence.mjs:

✅ 1 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s)

Not empty-frontmatter: this changes published bundle contents. Not patch: it removes
behaviour a narrow consumer could depend on, and this repo labels its own breaking changes
minor. major is forbidden for the fixed group and
scripts/check-changeset-no-major.mjs passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YBWFb5YgMU5dw8p2VKj16S

Generated by Claude Code